jrAparna module
Using Jamroom
If you change a modules template in the file system, then whenever a new module is released the change will disappear.
The problem is:
* skins that don't override modules will have no issue.
* skins that require an override of a module template in order to fit into the skin wont work with a default module made by aparna because the modules template wont have been customized to fit the skin.
Using aparna to create a module that doesnt fit with the skin causes:
"I made this with aparna, but it doesnt work" type questions to be asked, to which the answer is "It will work but you have to customize the templates now", to which the response is "How do I do that without code, im not a coder".
Which leaves us at a point where we need to do direct customizations to individual sites each time the module is used.
Thats not a good structure, so its better to retire the module and let those that will make modules make them, and not give half finished modules to those that dont really want to make modules.
